tempo-k8s docs - Retention period configuration

Traces are large, and production deployments can very rapidly generate large amounts of data that can be expensive to store. One of the ways to limit the amount of storage that your Tempo deployment can consume is to configure a maximum retention period. This will configure the compactor component of the deployment to periodically delete all traces older than that limit. The baseline, recommended limit (which is also the default in tempo-coordinator-k8s), is 30 days.

Depending on your operational needs (and your storage capabilities), you can choose to increase or decrease that limit a will.

You can configure the retention period on tempo-coordinator-k8S through its retention-period config option.

For example:

juju config tempo retention-period=24

Last updated a month ago.